chore(security): exclude GHSA-w4pp-8pjf-rmxw pacote DoS advisory - #9584
Merged
mohammadalfaiyazbitgo merged 1 commit intoAug 27, 2026
Merged
Conversation
pacote's addGitSha() has a DoS via malicious spec.rawSpec (CVE-2026-9496, CVSS 7.7). pacote is only pulled in transitively via dev/build tooling (lerna pinned to pacote@21.0.1, @npmcli/arborist, yeoman-generator) and never processes untrusted input - specs come only from our own package.json/yarn.lock. No fixed pacote version is compatible with lerna's current pin, so exclude per existing pattern in osv-scanner.toml. TICKET: WEB-000
mohammadalfaiyazbitgo
force-pushed
the
mohammadalfaiyaz/WEB-000-osv-pacote-exclusion
branch
from
August 27, 2026 17:12
b94faf6 to
80afcd1
Compare
mohammadalfaiyazbitgo
marked this pull request as ready for review
August 27, 2026 17:34
mohammadalfaiyazbitgo
requested review from
davidkaplanbitgo and
rishikeshdadam136
August 27, 2026 17:34
danielpeng1
approved these changes
Aug 27, 2026
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Release CI (
Enforce Vulnerability Severity Threshold) started blocking releases after a new HIGH-severity advisory, GHSA-w4pp-8pjf-rmxw (CVE-2026-9496, CVSS 7.7), was published today againstpacote— a DoS inaddGitSha()triggered by a maliciousspec.rawSpec.Why it's safe to exclude
pacoteonly enters our tree transitively via dev/build tooling:lerna(pinned topacote@21.0.1exactly),@npmcli/arborist,@npmcli/metavuln-calculator, andyeoman-generator(^15.2.0, used byyarn sdk-coin:new).pacoteuntrusted/attacker-controlled specs — inputs come only from our ownpackage.json/yarn.lockand lerna's internal publish/version flow.pacote@21.5.1/22.0.0, and no version satisfying lerna's exact21.0.1pin exists yet, so we can't bump without breaking the release/publish pipeline.osv-scanner.toml.What
Adds one
[[IgnoredVulns]]entry forGHSA-w4pp-8pjf-rmxwwith the justification above.Follow-up: re-evaluate once lerna/arborist/yeoman-generator bump to a pacote version ≥21.5.1.